fix(dependencies): restrict mcp version to <=1.27.1 to prevent breaki… - #2278
fix(dependencies): restrict mcp version to <=1.27.1 to prevent breaki…#2278grabear wants to merge 1 commit into
Conversation
…ng changes in mcp 2.0.0
|
Closes #2277 |
There was a problem hiding this comment.
Looks safe to merge — no coupling regressions and no blocking issues, checked against the code graph (not a self-assessment).
Graphify reviewed this change.
Looks safe to merge — no coupling regressions and no blocking issues, checked against the code graph (not a self-assessment).
Graphify review — findings
This PR pins the mcp optional dependency to <=1.27.1 in pyproject.toml (previously unbounded), updating both the mcp extra definition and the corresponding uv.lock requirement entry. The remainder of the uv.lock changes adjust dependency environment markers across many transitive packages (e.g., broadening or removing python_full_version constraints), which appear to be a lockfile re-resolution triggered by the version cap. The surface area is limited to packaging/dependency metadata; no application source code is modified.
Worth a look
- mcp extra now caps mcp at <=1.27.1, blocking newer releases —
pyproject.toml:55· Escalate · medium- agreed by 2 of 2 members but NOT verified (no proof, no reproducing execution) — consensus is not a verdict; needs human review
Analysis details — impact, health, verification
Impact & health
graphify review
Impact — 1 function(s) in the blast radius of 1 changed node(s).
Health — grade A; no new coupling regressions.
Verification — 1 function(s) need re-proving (callee-first):
pkg_graphifyy
Gate & verification
graphify gate
PASS — objectively clean (no health regressions, tests not run — proofs not enforced this run (re-run with --prove to verify the blast radius)). Grounded, not self-assessed.
Advisory (not blocking):
- verification_scope: 1 function(s) in blast radius — re-run with
--proveto formally verify them
…ng changes in mcp 2.0.0